when subscriber can not get argo pod logs, make pod log message intuitive #4926
+434
−27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Fix: #4532
When subscriber pods fail to get from workflow pod or CR pod, the imported logs always return the same value. This is not intuitive for users.
So, by getting the phase state from the chaos experiment run, make the log message different for each experiment phase.
But the problem remains. I'm not sure which is the best way to write the logs.